Connecting to multiple cloud instances in a telecommunications network

ABSTRACT

Aspects of the disclosure involve systems and methods for utilizing Virtual Local Area Network separation in a connection, which may be a single connection, between a customer to a telecommunications network and a cloud environment to allow the customer to access multiple instances within the cloud through the connection. A customer may purchase multiple cloud resource instances from a public cloud environment and, utilizing the telecommunications network, connect to the multiple instances through a communication port or connection to the cloud environment. To utilize the single connection or port, communication packets intended for the cloud environment may be tagged with a VLAN tag that indicates to which cloud instance the packet is intended. The telecommunications network may route the packet to the intended cloud environment and configure one or more aspects of the cloud environment to analyze the attached VLAN tag to transmit the packet to the intended instance.

TECHNICAL FIELD

Embodiments of the present invention generally relate to systems andmethods for implementing a telecommunications network, and morespecifically for utilizing Virtual Local Area Network (VLAN) separationin a connection between a customer to the network and a public cloudenvironment to allow the customer to access multiple instances withinthe cloud through the connection.

BACKGROUND

Telecommunication networks provide for the transmission of informationacross some distance through terrestrial, wireless or satellitecommunication networks. Such communications may involve voice, data ormultimedia information, among others. In addition, telecommunicationnetworks often offer features and/or services to the customers of thenetwork that provide flexible and varied ways in which thecommunications are transmitted over the network. For example, sometelecommunication networks provide Internet access to its customers,long distance communication capabilities, high definition audio and/orvideo communication capabilities, and the like. In other examples, thetelecommunication network may be utilized to provide connectivity to oneor more cloud-based resources offered by a third party. In other words,customers may purchase resources from a public cloud service tovirtualize one or more of their processes and connect to such resourcesthrough a telecommunications network.

Often times, customers purchase multiple resources from the public cloudservice. For example, a customer may purchase a group of resources (suchas data storage resources, processing resources, security resources, andthe like) for each step in a process, such as a group of resources fordevelopment, a group for testing, and a group for manufacturing.Further, the cloud environment may maintain a separation between thegroups of resources within the cloud environment so that use of onegroup of resources does not negatively affect other groups used by thecustomer. Each group of resources may be referred to as a “segment” or“instance” of cloud resources within the cloud environment. Typically,however, the customer is connected to each cloud instance through anindividual private connection between a customer port and the cloudinstance to maintain the separation of the instances. Thus, if acustomer purchases three cloud instances, three connections to theinstances are made through the connectivity network. The multipleconnections typically take a longer time to establish between thecustomer and the cloud environment, reducing the flexibility andefficiency of the connectivity network in providing the customer thecloud resources.

SUMMARY

Aspects of the present disclosure involve systems and methods forconnecting to multiple cloud instances from a singleport of a network. Afirst plurality of communication packets from a first device is receivedfrom a single port, where the first plurality of communication packetsare associated with a first Virtual Local Area Network identifier. Inaddition, a second plurality of communication packets from the firstdevice is received from the single port as well, where the secondplurality of communication packets is associated with a second VirtualLocal Area Network identifier. In embodiments, the first Virtual LocalArea Network identifier is associated with a first cloud computinginstance in a cloud computing environment and the second Virtual LocalArea Network identifier is associated with a second cloud computinginstance in the cloud computing environment. At least one device, suchas an edge device, router, or the like, of the cloud environment isconfigured, such as through an API, to route the packets, based on thedistinct VLAN identifiers. For example, the first plurality ofcommunication packets associated with the first Virtual Local AreaNetwork identifier are then routed to a first edge device of the cloudcomputing environment for connection to the first cloud computinginstance, and the second plurality of communication packets associatedwith the second Virtual Local Area Network identifier is routed to afirst edge device of the cloud computing environment for connection tothe second cloud computing instance. Accordingly, distinct connectionswith the first device, which may be a customer device, are not requiredto establish distinct connections with instances in the cloud.Similarly, distinct VLANs through a network, such as a backbone network,between the customer and the cloud are also not required, among otheradvantages.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating a first network environmentfor providing connectivity between a customer to a telecommunicationsnetwork and multiple instances of a cloud environment.

FIG. 2 is a schematic diagram illustrating a second network environmentfor providing connectivity between a customer to a telecommunicationsnetwork and multiple instances of a cloud environment.

FIG. 3 is flowchart illustrating a method for utilizing Virtual LocalArea Network (VLAN) separation in a connection between a customer to anetwork and a public cloud environment.

FIG. 4 is a diagram illustrating an example of a computing system whichmay be used in implementing embodiments of the present disclosure.

DETAILED DESCRIPTION

Aspects of the present disclosure involve systems, methods, computerprogram products, and the like, for utilizing Virtual Local Area Network(VLAN) separation in a connection, which may be a single connection,between a device, which may be a customer device or a first network, anda cloud environment, which may be a public or private cloud, to allowthe customer device to access multiple instances within the cloudthrough the connection. Through the systems and methods described, thecustomer operating the customer device may purchase multiple cloudresource instances from a public cloud environment and, utilizing thetelecommunications network, connect to the multiple instances through acommunication port or single connection of the customer the device tothe cloud environment by way of the intervening network. This mayreplace the conventional configuration of providing individualconnections or ports between the customer device/first network and eachinstance of the cloud resources. To utilize the single connection orport, communication packets intended for the cloud environment may betagged with a VLAN tag that indicates to which cloud instance the packetis intended. The telecommunications network may route the packet to theintended cloud environment. In advance, the cloud environment isconfigured to recognize the VLAN tags in any inbound traffic,particularly traffic associated with the customer port, to analyze theattached VLAN tag to transmit the packet to the intended instance. Thus,rather than providing multiple tunnels between the customer, whether acustomer device or the first network, and the cloud environment, one foreach cloud instance, a single tunnel may be utilized to provide alltraffic to the cloud environment for all instances used by the firstnetwork. This configuration may also allow for a faster connection fromthe customer to new cloud instances through the telecommunicationsnetwork.

FIG. 1 is a schematic diagram illustrating a first network environment100 illustrating the limitations of multiple connections to cloudenvironment 142. The first network environment 100, for example,provides connectivity between a customer 122 and multiple instances of acloud environment 142 by way of a telecommunications network 102. Thetelecommunications network 102 provides a connection between thecustomer devices or network 122 and the cloud 142, which may be a publicvirtual cloud, such that the customer may request resources from thepublic cloud and access those resources through the network. Inparticular, customer network may purchase resources from the virtualcloud environment 142 to execute processes on the resources. To utilizethose purchased resources, the telecommunications network 102 mayprovide a connection between the customer's devices 110 (referred tosometimes herein as simply the “customer”) and the virtual cloudenvironment 142. More particularly, the customer's devices may connectto and provide/receive data and packets through a provider edge 132, thenetwork 102, and a provider edge 131. As explained in more detail below,the connection facilitated by the network 102 may be a connection over apublic portion of the network 102 or a connection over a private ordedicated portion of the network. Regardless of the type or construct ofthe connection, the network 102 thus provides a communication pathbetween the customer 106 and the virtual cloud environment 142 tofacilitate the use of cloud resources by the customer.

The network 102 may include a series of interconnected networkingdevices, such as routers and switches, that receive a communication,analyze the communication to determine a destination, and route thecommunication to a connected networking device to get the communicationcloser to a destination or egress point (such as provider edge 131). Todetermine which routes through the network to utilize to route areceived communication or packet, components of the network may receiveroute information through one or more route announcing sessions betweenthe devices. These route announcing sessions provide Layer 3 routinginformation between the components of the network and between differentnetworks so that components of the telecommunications network 102 andother networks may determine how to route received communicationpackets.

In a conventional setting, the customer 122 is connected to each cloudinstance through multiple individual private connections 130, 132, 134between a customer port and each cloud instance to maintain theseparation of the instances.

As discussed above, the customer 122 may purchase or otherwise utilizemultiple cloud instances 104-108 for the execution of the customerprocesses. The multiple instances 104-108 may be utilized for a varietyof reasons, such as, but not limited to, security concerns, redundancy,performance metrics, and the like. The separation of the cloud instances104-108 may be virtual within the virtual cloud environment or may bephysically separate on different physical resource devices. Regardlessof the mechanism or technique to separate the cloud instances 104-108 inthe cloud environment 142, the customer 122 may be connected to eachinstance through the network 102. In one particular embodiment, thenetwork 102 provides a separate connection between the customer 122 andeach instance 104-108 in the cloud environment 142. For example,connection A 130 provides connection to cloud instance 104 (e.g.,storage resources), while connection B 132 provides connection to cloudinstance B 106 (e.g., processing resources) and connection C 134provides connection to cloud instance C 108 (e.g., security resources).As should be appreciated, the multiple connections 130, 132, 134 betweenthe customer 122 and the instances 104-108 may include additional coststo set up for the network 102 and may be inefficient to provide theconnection to the cloud services to the customer.

Although illustrated as separate connections 110-114 in the network 100of FIG. 1, it should be appreciated that various configurations may beutilized in connecting the customer 122 to the cloud environment 142.For example, the customer 122 may connect to the network 102 through oneor more communication ports, sometimes referred to as a User NetworkInterface (UNI). Through the UNI, the network 102 receives thecommunication packets intended for the cloud environment 142. In asimilar manner, the network 102 may communicate with the cloudenvironment 142 through one or more communication ports. Further, anexchange of routing information, such as Border Gateway Protocol (BGP)information, may occur to allow network 102 to transmit and receivepackets from the customer 122 and the cloud environment 142 at a Layer 3communication level. Similarly, the network 102 may announce or exchangerouting information (such as IGP) within the network to routecommunications between provider edges of the network. In general, BGPinformation (or BGP session, BGP feed or BGP data) is a table ofInternet Protocol (IP) prefixes which designate network connectivitybetween autonomous systems (AS) or separate networks. BGP informationfor a network route may include path (including next-hop information),network policies, and/or rule-sets for transmission along the path,among other information. The BGP feed may also include Interior GatewayProtocol (IGP) information for network routes within an AutonomousSystem (AS) or network and/or other network information that pertains tothe transmission of content from the network. However, BGP informationmainly describes routes used by the network 102 to connect to externalnetworks or customers (such as border network 122 and virtual cloudenvironment 142) while IGP information describes routes through thenetwork to connect one provider edge (such as provider edge 132) toanother provider edge (such as provider edge 131) through atelecommunications network 102. In addition to the Layer 3 connection,the network 102 may establish a private Layer 2 connection between thecustomer 122 and the cloud environment 142. This Layer 2 connection110-114, sometimes referred to as a Peer-To-Peer (P2P) connection,allows for a secure communication of packets between the customer 122and each instance 104-108 of the cloud environment 142. Thus, the Layer2 connection provides a private communication tunnel between thecustomer 122 and a cloud instance 104-108 through the network 102.

Providing individual P2P connections between the customer 122 and thecloud instances 104-108 may provide some benefits to the customer suchas secure communication paths and lower bandwidth requirement pertunnel. However, setting up individual communication tunnels 110-114 maytake significant time and coordination between the customer 122 and thenetwork 102 for each new instance 104-108 created in the cloudenvironment 142 upon a request from the customer. Provided with theability to dynamically request additional cloud resources 104-108 in thecloud environment 142 and establish Layer 2 communications between thecustomer 122 and the cloud 142 through the network 102 quickly mayimprove the overall usage and performance of the network in providingcloud access to the customer.

FIG. 2 is a schematic diagram illustrating a second network environment200 for providing connectivity between a customer 222 to atelecommunications network 202 and multiple instances 204-208 of a cloudenvironment 242, which provides the advantage of a single connection 216instead of multiple connections. For simplicity, FIG. 2 shows a singleconnection 216 between a single customer (customer 222) and multiplecloud instances 204-208 of cloud environment 242. However, in someembodiments, the single connection 216 can be multi-tenant, which canallow for multiple VLANs within each of multiple customers on the samephysical interconnection (e.g., single connection 216 can handle morecustomers than just customer 222). For example, while the connection tocloud environment 242 can be between a UNI point (or communication port)on a device (router, switch) on customer 222 to a port of provider edge210, the connection can also be between a single connection's 216multi-port (connecting multiple customers) device (e.g., router, switch)on customer 222 that's a Link Aggregation Group (LAG) connection toprovider edge 210. LAG connections allow a switch/router (e.g.,multi-port device on customer 222) to treat multiple physical linksbetween two end-points as a single logical link. Thus, network 202 cantreat a LAG connection on provider edge 210 to customer 222 device as ifit were a single physical port (e.g., multiple customers are treated asbeing on the same, common port on customer 222 device). Regardless ofthe number of customers connected to single connection 216, eachcustomer follows the same environment and methodology for customer 222described below.

Similar to the network configuration 100 of FIG. 1, the network 200 ofFIG. 2 includes a customer 222 connected to multiple instances 204-208of a virtual cloud environment 242 through the network 202. However, inthe network embodiment 200 of FIG. 2, the packets intended for themultiple cloud instances 204-208 may be transmitted to the cloudenvironment 242 over a single connection 216 such that communicationbetween the customer 222 and additional instances may occur without theneed to create additional communication tunnels through the network 202.Rather, through the use of VLAN tags 220, 222, 224 included in thepacket stream from the customer 222 to the network associated with themultiple instances 204-208 of the cloud environment 242, a singleconnection 216 may be established between the customer and the cloud tofacilitate communication between the environments.

Packets may be routed to specific cloud instances based on the VLAN tagincluded within the packets. In the example of FIG. 2, packets with VLANtag A 220 are routed to cloud instance A 204 (e.g., storage resources),while packets with VLAN tag B 222 are routed to cloud instance B 206(e.g., processing resources) and packets with VLAN tag C 224 are routedto cloud instance C 208 (e.g., security resources). In this way, while asingle connection 216 is used to connect to cloud environment 242,communication can be differentiated between different cloud instances.This makes second network environment 200 more flexible, efficient, andscalable than first network environment 100, which requires separateconnections for each type of resource. The particulars of utilizing VLANtags within the packet stream from the customer 222 to communicate withthe multiple instances 204-208 of the cloud environment 242 is discussedin more detail below with reference to the method 300 of FIG. 3.

For simplicity, FIG. 2 illustrated the second network environment 200providing connectivity between a customer(s) 222 to multiple instances204-208 of a cloud environment 242 through telecommunications network202. However, it is also contemplated that in some embodiments thetelecommunications network 202 can interconnect two cloud environmentsinstead of interconnecting a customer to a cloud environment.

FIG. 3 is a flowchart illustrating a method 300 for utilizing VLANseparation through VLAN tags in a communication connection between acustomer to a network and a public cloud environment. The operations ofthe method 300 may generally be executed by the network 202 illustratedin FIG. 2 to facilitate access to one or more cloud instances 204-208 ofthe cloud environment 242 by the customer 222 or customer devices. Inparticular, one or more components of the network 202 or an operator ofthe network may perform one or more of the operations of the method 300.In other embodiments, other networking or computing components mayperform operations of the method 300, such as components of the customer222. Further, the operations are discussed herein with reference to thenetwork 200 configuration illustrated in FIG. 2. Through the method 300,a single connection between the customer 222 and the cloud environment242 may be utilized to communicate with multiple instances 204-206 ofthe cloud through the telecommunications network 202.

Beginning in operation 302, the network 202 may receive a request fromthe customer 222 (such as a customer device in a customer location) toconnect to an instance in the cloud environment 242. The request may beto connect to multiple instances 204-208 or a newly established instancein the cloud environment 242. For example, the customer 222 (or anadministrator of the customer network) may purchase or otherwise requestaccess to one or more resources 204-208 of the cloud environment 242. Asmentioned above, such resources 204-208 may be data storage, computeresources, security resources, or any other virtual resource availablefrom a virtual cloud environment. Once the resources 204-208 arepurchased or obtained, the customer 222 (or administrator) may contactthe network 202 (such as an administrator of the network) to request acommunication connection to the cloud environment 242 to access thepurchased cloud resources. The network 202 may, in turn, begin a processto provide communication between the customer 222 and the instances204-208 in the cloud environment.

In operation 304, the customer provides connectivity information betweenthe customer 222 and the cloud environment 242. In one embodiment, thecustomer 222 connects to provider edge 210 of network 202 overconnection 214 to receive communications from the customer and providecommunications intended for the customer. Thus, network 202 may provideat least one communication port (or UNI) of provider edge 210 throughwhich communication with the customer 222 may occur. To establish theconnection 214, customer 222 and network 202 may exchange Layer 3routing information (such as through a BGP session) and Layer 2transport information. In addition to providing for transmission ofcommunication packets between the customer 222 and the network 202,connection 214 may also provide for transmission of the customer-cloudconnectivity information. More particularly, customer 222 may provide anidentifier of the instances 204-208 of the cloud environment 242associated with the customer 222. Further, the customer 222 may providea particular VLAN tag or other VLAN identifier that the customerassociates with each instance 204-208. For example, VLAN-A tag may beassociated with instance A 204, VLAN-B tag may be associated withinstance B 206, and so on. The VLAN identifiers may be any identifierutilized by the customer 222 to associate with a cloud instance 204-208utilized by the customer.

In another example, the customer 222 provides authentication informationprovided to the customer by the cloud environment 242 upon request foruse of the cloud instances 204-208. In other words, the customer 222 mayreceive an account identifier from the cloud environment 242 thatidentifies the customer to the cloud. This information may then beprovided to the network 202 such that the network may configure one ormore aspects of the cloud environment 242 on behalf of the customer, asexplained in more detail below.

With the customer-cloud connectivity information received, the network202 may then configure one or more devices of the network to connect thecustomer port of provider edge 210 to an egress port of provider edge212 to the cloud environment 242 in operation 306. In one particularembodiment, the network 202 may establish, through shared IGPinformation, a communication route or path 218 through the networkbetween provider edge 210 connected to the customer 222 and provideredge 212 connected to the cloud environment 242. The createdcommunication path through the network 202 may include configuring oneor more of the network components to receive and/or transmit packetsthat include the VLAN tags of the packet stream from the customer 222.In one embodiment, the egress port to the cloud environment 242 maysimilarly be a UNI communication port.

In operation 308, the network 202 configures one or more assets of thecloud environment 242 associated with the network. For example, thenetwork 202 may purchase or otherwise establish a connection 216 betweenthe network and the cloud environment 242. In some instances, thisincludes requesting a communication port with the cloud environment 242through which the network 202 may provide communication packets orframes. As such, the network 202 may have an identifier with the cloudenvironment 242 that the cloud may use to identify the network 202. Inaddition, Layer 3 information (such as BGP information) may be exchangedbetween the network 202 and the cloud environment 242 to establish acommunication path between the networks. With the account informationand BGP information, the cloud environment 242 may provide an open portwith the provider edge 212 of the network 202 to receive communicationpackets intended for the cloud.

Once a communication port is provided and a communication link 216established, the network may configure the cloud port to accept the VLANtagged packets from the customer 222. In particular, the network 202 maycall one or more Application Programming Interfaces (APIs) 250 tocommunicate with and configure aspects of the cloud environment. Throughthe APIs 250, the network 202 may provide the VLAN tags received fromthe customer 222 to the cloud environment 242 that are associated withthe cloud instances 204-208 utilized by the customer. With theconnection 216 established and the VLAN information, the cloudenvironment 242 may create a virtual interface associated with thecommunication port of the connection 216 to manage the receipt andtransmission of packets on the path. This virtual interface may beprovided with the VLAN tag identifiers for use by the cloud environment242 as explained below.

Further, in operation 310, the network 202 may call one or more APIs 250of the cloud environment 242 to associate the VLAN information of thecustomer 222 with the instances 204-208 within the virtual interface ofthe cloud. For example, the network 202 may instruct the cloudenvironment 242 to create a virtual gateway between the communicationport at the cloud and a particular instance 204 utilized by the customer222. The virtual gateway may then be associated with a particular VLANtag or identifier that the customer 222 uses to identify packetsintended for the particular instance 204 of the cloud environment 242.Similar virtual gateways may also be established for the other instances206, 208 of the cloud environment 242 with their own unique VLANidentifiers. In one embodiment, the network 222 may also provide one ormore authentication tokens provided to the customer 222 from the cloudenvironment 242 when the customer requested access to the cloudinstances 204-208. The authentication token thus delegates the network202 to configure the cloud environment 242 on behalf of the customer222.

Through the method 300 of FIG. 3, the network 202 may establish aprivate Layer 2 communication path between the customer 222 and thecloud instances 204-208. In particular, the network 202 may establish aVPN for communication with each instance 204-208 through the networkfrom the customer 222. With the VPN established for each instance204-208, the customer may tag (or otherwise include) an associated VLANidentifier with communication packets or frames intended for theparticular instances of the cloud environment. By combining the VLANtagged packets into a single stream of packets (or otherwisetransmitting the VLAN tagged packets along the communication path214-218 to the cloud environment 242), the customer 222 may transmit astream of packets intended for the cloud instances 204-208 through thenetwork 202 to the cloud environment 242 over a single communicationconnection 216. Further, the cloud environment 242 may then beconfigured to recognize or determine the VLAN tags included in headersof each of the received packets and, after associating the VLAN tags toa particular cloud instance 204-208, provide the packets to the intendedcloud instance 204-208. In this manner, the network 202 facilitates thecustomer 222 multiplexing communications between the customer andmultiple cloud instances 204-208 into a single stream of packets thatcan be transmitted on a route or path through the network. This mayremove having individual Layer 2 private connections between thecustomer 222 and each instance 204-208 of the cloud environment 242.

Several advantages may be realized for the customer 222 and/or thenetwork 202 through the use of VLAN separation in a connection betweenthe customer to the network and a cloud environment 242 to allow thecustomer to access multiple instances 204-208 within the cloud throughthe connection. For example, a single route through the network 202 maybe easier to manage for the customer 222 by an administrator of thenetwork and for the customer itself by consolidating several secureroutes or tunnels through the network 202 into a single route andapplying global routing features to the route. Further, creating orsetting up the routes between the customer 222 and the cloud environment242 may occur faster (due to the fewer number of components to beconfigured) and, in some instances, may be created dynamically inresponse to a request by the customer. For example, the customer 222 maybe provided with a mechanism to dynamically request a connection to thecloud environment 242 or a cloud instance 204 by providing the routingand connectivity information to a network device. The network device maythen automatically configure the ports of the network 202 and thecontrollable aspects of the cloud environment 242 through calling one ormore APIs 250 of the cloud to create the connection or route. Tearingdown a route to the cloud environment 242 may also occur dynamically ina similar manner. In addition, fewer routes provided to the customer 222by the network 202 may provide the network with more resources anddevices to provide services to other customers. Thus, by utilizing VLANtags to separate packets intended for multiple cloud instances 204-208,the network 202 may operate more efficiently and provide the customer222 a better service in connecting to the cloud environment 242.

FIG. 4 is a block diagram illustrating an example of a computing deviceor computer system 400 which may be used in implementing the embodimentsof the components of the network disclosed above. For example, thecomputing system 400 of FIG. 4 may be the monitoring device discussedabove. The computer system (system) includes one or more processors402-406. Processors 402-406 may include one or more internal levels ofcache (not shown) and a bus controller or bus interface unit to directinteraction with the processor bus 412. Processor bus 412, also known asthe host bus or the front side bus, may be used to couple the processors402-406 with the system interface 414. System interface 414 may beconnected to the processor bus 412 to interface other components of thesystem 400 with the processor bus 412. For example, system interface 414may include a memory controller 418 for interfacing a main memory 416with the processor bus 412. The main memory 416 typically includes oneor more memory cards and a control circuit (not shown). System interface414 may also include an input/output (I/O) interface 420 to interfaceone or more I/O bridges or I/O devices with the processor bus 412. Oneor more I/O controllers and/or I/O devices may be connected with the I/Obus 426, such as I/O controller 428 and I/O device 430, as illustrated.The system interface 414 may further include a bus controller 422 tointeract with processor bus 412 and/or I/O bus 426.

I/O device 430 may also include an input device (not shown), such as analphanumeric input device, including alphanumeric and other keys forcommunicating information and/or command selections to the processors402-406. Another type of user input device includes cursor control, suchas a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to the processors 402-406and for controlling cursor movement on the display device.

System 400 may include a dynamic storage device, referred to as mainmemory 416, or a random access memory (RAM) or other computer-readabledevices coupled to the processor bus 412 for storing information andinstructions to be executed by the processors 402-406. Main memory 416also may be used for storing temporary variables or other intermediateinformation during execution of instructions by the processors 402-406.System 400 may include a read only memory (ROM) and/or other staticstorage device coupled to the processor bus 412 for storing staticinformation and instructions for the processors 402-406. The system setforth in FIG. 4 is but one possible example of a computer system thatmay employ or be configured in accordance with aspects of the presentdisclosure.

According to one embodiment, the above techniques may be performed bycomputer system 400 in response to processor 404 executing one or moresequences of one or more instructions contained in main memory 416.These instructions may be read into main memory 416 from anothermachine-readable medium, such as a storage device. Execution of thesequences of instructions contained in main memory 416 may causeprocessors 402-406 to perform the process steps described herein. Inalternative embodiments, circuitry may be used in place of or incombination with the software instructions. Thus, embodiments of thepresent disclosure may include both hardware and software components.

A machine readable medium includes any mechanism for storing ortransmitting information in a form (e.g., software, processingapplication) readable by a machine (e.g., a computer). Such media maytake the form of, but is not limited to, non-volatile media and volatilemedia. Non-volatile media includes optical or magnetic disks. Volatilemedia includes dynamic memory, such as main memory 416. Common forms ofmachine-readable medium may include, but is not limited to, magneticstorage medium; optical storage medium (e.g., CD-ROM); magneto-opticalstorage medium; read only memory (ROM); random access memory (RAM);erasable programmable memory (e.g., EPROM and EEPROM); flash memory; orother types of medium suitable for storing electronic instructions.

Embodiments of the present disclosure include various steps, which aredescribed in this specification. The steps may be performed by hardwarecomponents or may be embodied in machine-executable instructions, whichmay be used to cause a general-purpose or special-purpose processorprogrammed with the instructions to perform the steps. Alternatively,the steps may be performed by a combination of hardware, software and/orfirmware.

The description above includes example systems, methods, techniques,instruction sequences, and/or computer program products that embodytechniques of the present disclosure. However, it is understood that thedescribed disclosure may be practiced without these specific details. Inthe present disclosure, the methods disclosed may be implemented as setsof instructions or software readable by a device. Further, it isunderstood that the specific order or hierarchy of steps in the methodsdisclosed are instances of example approaches. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the method can be rearranged while remaining within thedisclosed subject matter. The accompanying method claims presentelements of the various steps in a sample order, and are not necessarilymeant to be limited to the specific order or hierarchy presented.

It is believed that the present disclosure and many of its attendantadvantages should be understood by the foregoing description, and itshould be apparent that various changes may be made in the form,construction and arrangement of the components without departing fromthe disclosed subject matter or without sacrificing all of its materialadvantages. The form described is merely explanatory, and it is theintention of the following claims to encompass and include such changes.

While the present disclosure has been described with reference tovarious embodiments, it should be understood that these embodiments areillustrative and that the scope of the disclosure is not limited tothem. Many variations, modifications, additions, and improvements arepossible. More generally, embodiments in accordance with the presentdisclosure have been described in the context of particularimplementations. Functionality may be separated or combined in blocksdifferently in various embodiments of the disclosure or described withdifferent terminology. These and other variations, modifications,additions, and improvements may fall within the scope of the disclosureas defined in the claims that follow.

We claim:
 1. A method comprising: receiving, at a first edge device, a first plurality of communication packets from a first device associated with a single port, the first plurality of communication packets associated with a first Virtual Local Area Network identifier, and receiving, from the single port, a second plurality of communication packets from the first device, the second plurality of communication packets associated with a second Virtual Local Area Network identifier, the first Virtual Local Area Network identifier associated with a first cloud computing instance in a cloud computing environment and the second Virtual Local Area Network identifier associated with a second cloud computing instance in the cloud computing environment; routing, to a first edge device of the cloud computing environment, the first plurality of communication packets associated with the first Virtual Local Area Network identifier for connection to the first cloud computing instance and the second plurality of communication packets associated with the second Virtual Local Area Network identifier for connection to the second cloud computing instance; and providing the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier to one or more application programming interfaces of the cloud computing environment to establish routing of packets associated with the first Virtual Local Area Network identifier to the first cloud computing instance in the cloud computing environment and to distinctly route packets associated with the second Virtual Local Area Network identifier to the second cloud computing instance in the cloud computing environment.
 2. The method of claim 1, further comprising establishing a connection between the first device and the first edge device of the cloud computing environment by receiving, from the single port at the first device, a UNI port identifier that is for the single port, the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier, and Layer 2 and Layer 3 transport information.
 3. The method of claim 1, wherein the first cloud computing instance and the second cloud computing instance comprise a first virtual private cloud and a second virtual private cloud, respectively, and wherein the first virtual private cloud and the second virtual private cloud are segmented environments within the cloud computing environment establishing a first virtual gateway and a second virtual gateway between the first device and the cloud computing environment based on the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier, respectively.
 4. The method of claim 1, wherein the single port causes a transmission of all communication packets to all cloud computing instances on the cloud computing environment associated with the first device.
 5. The method of claim 1, wherein the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier are provided in headers of the respective first plurality of communication packets and the second plurality of communication packets from the single port to establish a multiplexed connection between a network of the first device to a second network of the first edge device comprising at least the first cloud computing instance and the second cloud computing instance of the cloud computing environment.
 6. The method of claim 1, the method further comprising: establishing a communication path between multiple networks and the cloud computing environment by: connecting one or more networks to the single port of the first device by a Link Aggregation Group connection to an egress port connected to the first edge device of the cloud computing environment in accordance with the communication path; and wherein the single port receives or transmits packets from multiple networks that include the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier of packet streams from the first device.
 7. An apparatus comprising: an edge device including one or more processors and a communication interface coupled to the one or more processors, wherein the edge device provides communication between a cloud computing environment and a single port of a first device, and wherein the one or more processors are configured to perform operations comprising: receiving, from the single port, a first plurality of communication packets from the first device, the first plurality of communication packets associated with a first Virtual Local Area Network identifier, and receiving, from the single port, a second plurality of communication packets from the first device, the second plurality of communication packets associated with a second Virtual Local Area Network identifier, the first Virtual Local Area Network identifier associated with a first cloud computing instance in the cloud computing environment and the second Virtual Local Area Network identifier associated with a second cloud computing instance in the cloud computing environment; routing, to a second edge device of the cloud computing environment, the first plurality of communication packets associated with the first Virtual Local Area Network identifier for connection to the first cloud computing instance and the second plurality of communication packets associated with the second Virtual Local Area Network identifier for connection to the second cloud computing instance; and providing the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier to one or more application programming interfaces of the cloud computing environment to configure at least the second edge device of the cloud computing environment to route packets associated with the first Virtual Local Area Network identifier to the first cloud computing instance in the cloud computing environment and to distinctly route packets associated with the second Virtual Local Area Network identifier to the second cloud computing instance in the cloud computing environment.
 8. The apparatus of claim 7, the one or more processors further configured to perform operations comprising: establishing a connection between the first device and the first edge device by receiving, from the single port at the first device, a UNI port identifier associated with the single port, the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier, and Layer 2 and Layer 3 transport information.
 9. The apparatus of claim 7, wherein the first cloud computing instance and the second cloud computing instance comprise a first virtual private cloud and a second virtual private cloud, respectively, and wherein the first virtual private cloud and the second virtual private cloud are segmented environments within the cloud computing environment establishing a first virtual gateway and a second virtual gateway between the first device and the cloud computing environment based on the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier, respectively.
 10. The apparatus of claim 7, wherein the single port causes a transmission of all communication packets to all cloud computing instances on the cloud computing environment associated with the first device.
 11. The apparatus of claim 7, wherein the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier are provided in headers of the respective first plurality of communication packets and the second plurality of communication packets from the single port to establish a multiplexed connection between a network of the first device to a second network of the first edge device comprising at least the first cloud computing instance and the second cloud computing instance of the cloud computing environment.
 12. The apparatus of claim 7, the one or more processors further configured to perform operations comprising: establishing a communication path between multiple networks and the cloud computing environment by: connecting one or more networks to the single port of the first device by a Link Aggregation Group connection to an egress port connected to a provider edge of the cloud computing environment in accordance with the communication path; and wherein the single port receives or transmits packets from multiple networks that include the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier of packet streams from the first device.
 13. A non-transitory computer-readable medium comprising instructions stored thereon, the instructions executable by one or more processors of a computing system to perform a method for dynamically requesting a network resource, the instructions causing the computing system to: receive, from a single port, a first plurality of communication packets from a first device, the first plurality of communication packets associated with a first Virtual Local Area Network identifier, and receive, from the single port, a second plurality of communication packets from the first device, the second plurality of communication packets associated with a second Virtual Local Area Network identifier, the first Virtual Local Area Network identifier associated with a first cloud computing instance in a cloud computing environment and the second Virtual Local Area Network identifier associated with a second cloud computing instance in the cloud computing environment; route, to a first edge device of the cloud computing environment, the first plurality of communication packets associated with the first Virtual Local Area Network identifier for connection to the first cloud computing instance and the second plurality of communication packets associated with the second Virtual Local Area Network identifier for connection to the second cloud computing instance; and provide the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier to one or more application programming interfaces of the cloud computing environment to establish routing of packets associated with the first Virtual Local Area Network identifier to the first cloud computing instance in the cloud computing environment and to distinctly route packets associated with the second Virtual Local Area Network identifier to the second cloud computing instance in the cloud computing environment.
 14. The non-transitory computer-readable medium of claim 13, the instructions causing the computing system to further: establish a connection between the first device and the first edge device by receiving, from the single port at the first device, a UNI port identifier that is for the single port, the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier, and Layer 2 and Layer 3 transport information.
 15. The non-transitory computer-readable medium of claim 13, wherein the first cloud computing instance and the second cloud computing instance comprise a first virtual private cloud and a second virtual private cloud, respectively, and wherein the first virtual private cloud and the second virtual private cloud are segmented environments within the cloud computing environment establishing a first virtual gateway and a second virtual gateway between the first device and the cloud computing environment based on the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier, respectively.
 16. The non-transitory computer-readable medium of claim 13, wherein the single port causes a transmission of all communication packets to all cloud computing instances on the cloud computing environment associated with the first device.
 17. The non-transitory computer-readable medium of claim 13, the instructions causing the computing system to further: establish a communication path between multiple networks and the cloud computing environment by: connecting one or more networks to the single port of the first device by a Link Aggregation Group connection to an egress port connected to a provider edge of the cloud computing environment in accordance with the communication path; and wherein the single port receives or transmits packets from multiple networks that include the first Virtual Local Area Network identifier and the second Virtual Local Area Network identifier of packet streams from the first device. 